On-demand transmission of aborted HARQ codebooks in mobile communications

ABSTRACT

An apparatus aborts a transmission of a first message of a first type of traffic in a first slot or sub-slot without resuming the transmission in the first slot or sub-slot. The apparatus then stores a payload of the first message. The apparatus later retransmits the payload in full in a second slot or sub-slot that is subsequent the first slot or sub-slot.

CROSS REFERENCE TO RELATED PATENT APPLICATION

The present disclosure is part of a non-provisional patent applicationclaiming the priority benefit of U.S. Provisional Patent Application No.62/853,779, filed on 29 May 2019, the content of which beingincorporated by reference in its entirety.

TECHNICAL FIELD

The present disclosure is generally related to mobile communicationsand, more particularly, to on-demand transmission of aborted hybridautomatic repeat request (HARQ) codebook(s) in mobile communications.

BACKGROUND

Unless otherwise indicated herein, approaches described in this sectionare not prior art to the claims listed below and are not admitted asprior art by inclusion in this section.

The Release 16 (Rel-16) of the 3^(rd) Generation Partnership Project(3GPP) Technical Specification (TS) for New Radio (NR) allowsconfiguration of two simultaneous codebook determination procedures. Forexample, one of the two simultaneous codebook determination procedurescould be for enhanced Mobile Broadband (eMBB) and the other forUltra-Reliable Low-Latency Communication (URLLC). In this example, eachdownlink control information (DCI) would channel the respectiveacknowledgement and negative acknowledgement (ACK/NACK) bits to one orthe other procedure. However, in case of collision between two HARQcodebooks of different priorities, the one with a lower priority (e.g.,codebook for eMBB) would be discarded (e.g., pre-empted/aborted iftransmission is ongoing). This would normally trigger retransmission ofall downlink (DL) packets that were acknowledged in the deprioritizedHARQ codebook. Therefore, there is a need for a solution to recover theaborted lower-priority (e.g., eMBB in this example) codebook.

SUMMARY

The following summary is illustrative only and is not intended to belimiting in any way. That is, the following summary is provided tointroduce concepts, highlights, benefits and advantages of the novel andnon-obvious techniques described herein. Select implementations arefurther described below in the detailed description. Thus, the followingsummary is not intended to identify essential features of the claimedsubject matter, nor is it intended for use in determining the scope ofthe claimed subject matter.

An objective of the present disclosure is to provide schemes, concepts,designs, techniques, methods and apparatuses pertaining to on-demandtransmission of aborted HARQ codebook(s) in mobile communications. Undervarious proposed schemes in accordance with the present disclosure, asolution for recovering aborted codebook(s) is introduced.

In one aspect, a method may involve a processor of an apparatus abortinga transmission of a first message of a first type of traffic in a firstslot or sub-slot without resuming the transmission in the first slot orsub-slot. The method may also involve the processor storing a payload ofthe first message. The method may further involve the processorretransmitting the payload in full in a second slot or sub-slot that issubsequent the first slot or sub-slot.

In another aspect, a method may involve a processor of an apparatusreceiving a trigger from a wireless network. The method may also involvethe processor reporting status of one or more HARQ processes to thewireless network responsive to receiving the trigger.

It is noteworthy that, although description provided herein may be inthe context of certain radio access technologies, networks and networktopologies such as 5^(th) Generation (5G)/NR, the proposed concepts,schemes and any variation(s)/derivative(s) thereof may be implementedin, for and by other types of radio access technologies, networks andnetwork topologies such as, for example and without limitation,Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro,Internet-of-Things (IoT), Industrial IoT (IIoT) and narrowband IoT(NB-IoT). Thus, the scope of the present disclosure is not limited tothe examples described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a furtherunderstanding of the disclosure and are incorporated in and constitute apart of the present disclosure. The drawings illustrate implementationsof the disclosure and, together with the description, serve to explainthe principles of the disclosure. It is appreciable that the drawingsare not necessarily in scale as some components may be shown to be outof proportion than the size in actual implementation to clearlyillustrate the concept of the present disclosure.

FIG. 1 is a diagram of an example network environment in which varioussolutions and schemes in accordance with the present disclosure may beimplemented.

FIG. 2 is a diagram of an example table summarizing various proposedschemes in accordance with the present disclosure.

FIG. 3 is a diagram of an example scenario in accordance with animplementation of the present disclosure.

FIG. 4 is a diagram of an example scenario in accordance with animplementation of the present disclosure.

FIG. 5 is a diagram of an example scenario in accordance with animplementation of the present disclosure.

FIG. 6 is a diagram of an example scenario in accordance with animplementation of the present disclosure.

FIG. 7 is a diagram of an example scenario in accordance with animplementation of the present disclosure.

FIG. 8 is a block diagram of an example communication system inaccordance with an implementation of the present disclosure.

FIG. 9 is a flowchart of an example process in accordance with animplementation of the present disclosure.

FIG. 10 is a flowchart of an example process in accordance with animplementation of the present disclosure.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Detailed embodiments and implementations of the claimed subject mattersare disclosed herein. However, it shall be understood that the disclosedembodiments and implementations are merely illustrative of the claimedsubject matters which may be embodied in various forms. The presentdisclosure may, however, be embodied in many different forms and shouldnot be construed as limited to the exemplary embodiments andimplementations set forth herein. Rather, these exemplary embodimentsand implementations are provided so that description of the presentdisclosure is thorough and complete and will fully convey the scope ofthe present disclosure to those skilled in the art. In the descriptionbelow, details of well-known features and techniques may be omitted toavoid unnecessarily obscuring the presented embodiments andimplementations.

Overview

Implementations in accordance with the present disclosure relate tovarious techniques, methods, schemes and/or solutions pertaining toon-demand transmission of aborted HARQ codebook(s) in mobilecommunications. According to the present disclosure, a number ofpossible solutions may be implemented separately or jointly. That is,although these possible solutions may be described below separately, twoor more of these possible solutions may be implemented in onecombination or another.

FIG. 1 illustrates an example network environment 100 in which varioussolutions and schemes in accordance with the present disclosure may beimplemented. FIG. 2˜FIG. 7 illustrate examples of implementation ofvarious proposed schemes in network environment 100 in accordance withthe present disclosure. The following description of various proposedschemes is provided with reference to FIG. 1˜FIG. 7.

Referring to part (A) of FIG. 1, network environment 100 may involve aUE 110 in wireless communication with a wireless network 120 (e.g., a 5GNR mobile network). UE 110 may be in wireless communication withwireless network 120 via a base station or network node 125 (e.g., aneNB, gNB or transmit-receive point (TRP)). Referring to part (B) of FIG.1, uplink (UL) transmission of HARQ codebooks for eMBB PUCCH may havealready been scheduled by DCI in slot n−1 and slot n when DCI schedulingUL transmission of HARQ codebook for URLLC arrives in slot n. As aresult, the UL transmission of the HARQ codebooks for eMBB, the priorityof which being lower than that of URLLC, may be aborted. Accordingly, UE110 may perform on-demand transmission of aborted HARQ codebook(s) inmobile communications based on any of the proposed schemes in accordancewith the present disclosure, as described herein.

Under a first proposed scheme in accordance with the present disclosure,in case of collision between two HARQ codebooks of different priorities,UE 110 may first abort UL transmission of information and/or dataassociated with a lower-priority codebook at the earliest without everresuming retransmission thereof. Next, under the first proposed scheme,UE 110 may store the actual raw payload bits (e.g., HARQ codebook) usingone of multiple options. In a first option (hereinafter referred to as“Option S1”), UE 110 may store the raw payload bits until they areoverwritten by the next cancellation (with one but not more codebookstored). In a second option (hereinafter referred to as “Option S2”), UE110 may utilize a first-in-first-out (FIFO) arrangement in storing theraw payload bits associated with each stored codebook until they areoverwritten by multiple cancellations. Under one approach in Option S2(hereinafter referred to as “Option S2a”), at a later time, UE 110 mayretrieve selected codebook(s) that is/are retransmitted given that arequest specifies, for each codebook, a slot (or sub-slot, depending onthe granularity of K1) where the original HARQ was scheduled. Underanother approach in Option S2 (hereinafter referred to as “Option S2b”),at a later time, UE 110 may retrieve all the FIFO content that isretransmitted given that a response specifies, for each codebook, theslot (or sub-slot, depending on the granularity of K1) where theoriginal HARQ was scheduled. In a third option (hereinafter referred toas “Option S3”), UE 110 may store the raw payload bits until they areoverwritten by the next HARQ codebook transmission, thereby supportingretransmission of a HARQ codebook regardless whether deprioritizationtook place or not.

Furthermore, under the first proposed scheme, UE 110 may retransmit infull later autonomously using originally assigned physical uplinkcontrol channel (PUCCH) resource(s) in a later slot (or sub-slot,depending on the granularity of K1). This may be performed following oneof Options S1, S2a and S3. Alternatively, under the first proposedscheme, UE 110 may retransmit in full upon being requested (e.g., bynetwork node 125), using independent, arbitrary resource(s), possiblycombined with other payload(s). This may be accomplished using one oftwo options. In a first option (hereinafter referred to as “Option R1”),UE 110 may transmit in full as a report when requested by a specificUL-DCI. This may be performed following one of Options S1, S2 and S3.For instance, a mechanism similar to that of aperiodic channel stateinformation (A-CSI) may be utilized. In a second option (hereinafterreferred to as “Option R2”), UE 110 may transmit in full upon receivingan implicit request (e.g., signaling in DL-DCI) to concatenate storeduplink control information (UCI) to new UCI. This may be performedfollowing one of Options S1 and S2. More detailed description of thefirst proposed scheme is provided below.

Under a second proposed scheme in accordance with the presentdisclosure, in case of collision between two HARQ codebooks of differentpriorities, UE 110 may transmit HARQ acknowledgement (HARQ-ACK) based oncurrent status of the HARQ process(es). For instance, network node 125may transmit a trigger (e.g., using an UL-DCI or a DL-DCI) and, inresponse, UE 110 may report the current ACK/NACK status for all the HARQprocesses configured by network node 125. Instead of having the statusof all the configured HARQ processes to be reported, the HARQprocess(es) for which UE 110 is to report the ACK/NACK may be signaledby network node 125 as part of the UL-DCI or DL-DCI. It is noteworthythat, under the second proposed scheme, there is no storage of payloadbits required. More detailed description of the second proposed schemeis provided below.

FIG. 2 illustrates an example table 200 summarizing above-describedproposed schemes in accordance with the present disclosure. That is,table 200 lists various combinations of storage, erasing andretransmission methods in implementing the proposed schemes. Forinstance, table 200 shows storage of payload content under Option S1 maybe implemented for a single last codebook, but not for a single selectedcodebook, multiple selected codebooks or all codebooks. As shown inTable 200, storage of payload content under Option S2s may beimplemented for a single last codebook, a single selected codebook ormultiple selected codebooks, but not for all codebooks. As shown inTable 200, storage of payload content under Option S2b may beimplemented for all codebooks, but not for a single last codebook, asingle selected codebook or multiple selected codebooks. As shown inTable 200, storage of payload content under Option S3 may be implementedfor all codebooks, but not for a single last codebook, a single selectedcodebook or multiple selected codebooks. As shown in Table 200, storageof payload content of automatic PUCCH may be implemented for a singlelast codebook, but not for a single selected codebook, multiple selectedcodebooks or all codebooks. As shown in Table 200, storage of payloadcontent of PUCCH may be implemented for a single last codebook, a singleselected codebook, multiple selected codebooks, all codebooks and allHARQ processes. As shown in Table 200, storage of payload content ofphysical uplink shared channel (PUSCH) may be implemented for a singlelast codebook, a single selected codebook, multiple selected codebooks,all codebooks and all HARQ processes.

Under the first proposed scheme, with respect to storage, UE 110 maystore the bits to be transmitted when a HARQ codebook transmission isaborted for prioritizing another transmission. In Option S1, in an eventthat a HARQ codebook transmission is aborted (and hence needs to bestored) when another HARQ codebook is already stored, the latestcodebook may overwrite the earlier one, with a maximum one codebookbeing stored at a time. In Option S2, in an event that a HARQ codebooktransmission is aborted and there is a limit on the number or total sizeof codebooks stored, the earliest HARQ codebook(s) may be overwritten bythe latest one, with more than one codebook being stored at a time. InOption S3, each HARQ codebook transmission, whether aborted or not, mayoverwrite content in the storage (e.g., a memory device in UE 110) whichmay store the last HARQ codebook at any given time. This feature may beutilized when PUCCH is transmitted as normal (e.g., node-prioritization) while network node 125, having failed to decode thePUCCH transmission, asks for retransmission. As an option, under theproposed scheme, aborted codebook(s) may not be overwritten bynon-aborted codebook(s).

Under the first proposed scheme, with respect to triggering ofretransmission and resource assignment, in Option R1 network node 125may send UL-DCI to UE 110 to trigger retransmission as PUSCH.Advantageously, since control information would be transmitted on PUSCHjust as A-CSI, the same mechanism may be utilized. Under a firstapproach in Option R1 (hereinafter referred to as “Option R1-1”), a newDCI field may be introduced. For instance, a single bit as the new DCIfield may be used to trigger retransmission. Alternatively, oradditionally, slot index (or indices) pointing back in time may be usedto select the codebook(s) requiring retransmission. Under a secondapproach in Option R1 (hereinafter referred to as “Option R1-2”), anexisting DCI field may be re-used to trigger retransmission. Forinstance, a radio resource control (RRC)-configurable special value ofan A-CSI-request field may trigger retransmission. Alternatively,multiple special values of the A-CSI-request field may triggerretransmission and may select between options on the content. As anexample, <special value #1> may specify the earliest codebook stored,and <special value #2> may specify all the codebooks stored.

Under the first proposed scheme, with respect to triggering ofretransmission and resource assignment, in Option R2, network node 125may send DL-DCI to UE 110 to trigger concatenation of stored HARQinformation (or parts thereof) to the currently selected codebook. Theconcatenated size may be used with the PRI field to select the PUCCHresource(s) used for transmission. Under a first approach in Option R2(hereinafter referred to as “Option R2-1”), a new DCI field may beintroduced for signaling. For instance, a single bit as the new DCIfield may be used to trigger concatenation. Alternatively, oradditionally, slot index (or indices) pointing back in time may be usedto select the codebook(s) requested for retransmission and to triggerconcatenation. Under a second approach in Option R2 (hereinafterreferred to as “Option R2-2”), an existing DCI field may be re-used forsignaling. As an example, a pre-configured special value of K1 orcombination of K1 and another field (e.g., HARQ) may triggerconcatenation. As another example, a pre-configured special value ofHARQ process identification (ID) (or special value in another fielddifferent from K1) may trigger concatenation. Under a third approach inOption R2 (hereinafter referred to as “Option R2-3”), implicit signalingmay be used (e.g., based on radio network temporary identifier (RNTI)and/or search space) to trigger concatenation. Under a fourth approachin Option R2 (hereinafter referred to as “Option R2-4”), concatenationmay be automatic to the earliest PUCCH that is transmitted next or aftera current slot or sub-slot.

FIG. 3 illustrates an example scenario 300 of implementing the firstproposed scheme in accordance with the present disclosure. In FIG. 3, anexample codebook format in retransmission in full is shown. In scenario300, when a codebook or a concatenation of codebooks is transmittedaccording to the first proposed scheme over PUSCH or PUCCH, the formatmay be, for example and without limitation: {slot #1, size #1, codebook#1, slot #2, size #2, codebook #2 . . . }. The slot (or sub-slot) andsize may be prepended to each codebook. The total size may also beprepended. Moreover, instead of bytes, 4-bit nibbles may be used as wellfor certain members within the format. Any variations and derivativesthereof are not precluded.

Under the first proposed scheme, with respect to payload content inretransmission, one of a number of options may be implemented. In afirst option, a specific single codebook may be retransmitted. Forinstance, at most a single codebook may be stored for retransmission.Alternatively, the earliest or the latest codebook may be retrieved forretransmission. In a second option, multiple codebooks may be selectedby DCI for retransmission. For instance, scheduling DCI may specify anordered list of pointers to selected previous slots (or sub-slots) wherede-prioritization took place to request retransmission of thecorresponding codebooks. In a third option, all codebooks may beretransmitted. For instance, the report may contain a pointer to aprevious slot (or sub-slot) for each codebook that is retransmitted,specifying where the abortion occurred. As an example, the ordered listmentioned above may be a bitmap (e.g., 16-bit bitmap) where each bit mayrepresent a slot (or sub-slot used as K1 unit). In an event thatretransmission is on PUSCH, with the allocation and modulation andcoding scheme (MCS) resulting in a larger bit size than the payload,then the latter may be zero-padded or padded with replicas.

FIG. 4, FIG. 5, FIG. 6 and FIG. 7 illustrate example scenario 400,example scenario 500, example scenario 600 and example scenario 700,respectively, of implementing the first proposed scheme in accordancewith the present disclosure.

Referring to FIG. 4, in scenario 400, at most a single codebook isstored and retransmitted over PUSCH. In scenario 400, at first, UE 110may receive from network node 125 a RRC signaling that configures aspecial value (e.g., a RRC-configurable special value of an A-CSI field)as a trigger to deprioritize a HARQ codebook for an eMBB traffic (e.g.,by indicating a scheduled transmission of a URLLC traffic, which isprioritized over the eMBB traffic). In response, UE 110 may storepayload bits of this HARQ codebook for retransmission at a later time.UE 110 may also prepend a size of the HARQ codebook to the payload.Next, UE 110 may schedule retransmission of the payload in a subsequentslot or sub-slot (e.g., as a result of receiving a UL-DCI signaling fromnetwork node 125). UE 110 may utilize the A-CSI reporting mechanism inretransmitting the payload (e.g., in a PUSCH).

Referring to FIG. 5, in scenario 500, at most a single codebook isstored and retransmitted over PUCCH. In scenario 500, at first, UE 110may receive from network node 125 a RRC signaling that configures aspecial value (e.g., a RRC-configurable special value of an A-CSI field)as a trigger to deprioritize a HARQ codebook for an eMBB traffic (e.g.,by indicating a scheduled transmission of a URLLC traffic, which isprioritized over the eMBB traffic). In response, UE 110 may storepayload bits of this HARQ codebook for retransmission at a later time.UE 110 may receive a trigger (e.g., DL-DCI with a pre-configured valuefor K1, which specifies HARQ ACK/NACK timing for a specific PDSCH) fromnetwork node 125. Accordingly, UE 110 may select a slot or sub-slotbased on the K1. UE 110 may also prepend the stored codebook to acurrent codebook appointed by the K1 to form concatenated codebooks. UE110 may further select a PUCCH based on a total size of the concatenatedcodebooks. Next, UE 110 may retransmit the concatenated codebooks in aPUCCH. In case the PUCCH is deprioritized then UE 110 may store theconcatenated codebooks.

Referring to FIG. 6, in scenario 600, multiple codebooks are stored in aFIFO arrangement and retransmitted together over PUSCH. In scenario 600,at first, UE 110 may receive from network node 125 a RRC signaling thatconfigures a special value (e.g., a RRC-configurable special value of anA-CSI field) as a trigger to deprioritize a HARQ codebook for an eMBBtraffic (e.g., by indicating a scheduled transmission of a URLLCtraffic, which is prioritized over the eMBB traffic). In response, UE110 may store payload bits of this HARQ codebook for retransmission at alater time. The size of the codebook may be prepended to content alreadyin storage, and FIFO arrangement may be utilized in overwriting existingstored payload. UE 110 may concatenate all stored codebooks, and UE 110may prepend a bitmap (e.g., 16-bit bitmap) pointing to previous slots orsub-slots of origin of all the stored codebooks. Next, UE 110 mayschedule retransmission of the payload in a subsequent slot or sub-slot(e.g., as a result of receiving a UL-DCI signaling from network node125). UE 110 may utilize the A-CSI reporting mechanism in retransmittingthe payload (e.g., in a PUSCH).

Referring to FIG. 7, in scenario 700, multiple codebooks are stored andretransmitted over PUSCH. In scenario 700, a HARQ codebook (e.g.,codebook 1) associated with an eMBB traffic scheduled for transmissionin slot n−7 may be deprioritized. Moreover, another HARQ codebook (e.g.,codebook 2) associated with the eMBB traffic scheduled for transmissionin slot n−1 may also be deprioritized. Then, codebook 1 and codebook 2may be concatenated for retransmission in slot n. A bitmap (e.g., 16-bitbitmap) may be prepended with bits indicating from which of a pluralityof previous slots or sub-slots codebook 1 and codebook 2 originated. Theretransmission may optionally include padding bid(s) as necessary.

Under the second proposed scheme, with respect to transmitting status ofHARQ process(es) on request, instead of storing the HARQ-ACK codebook analternative may be to transmit HARQ-ACK based on the status of currentHARQ process(es). In a first option, network node 125 may transmit atrigger (e.g., using UL-DCI or DL-DCI) to UE 110 and, in response, UE110 may report the current ACK/NACK status for all the HARQ processesconfigured by network node 125. In a second option, network node 125 maytransmit a trigger (e.g., using UL-DCI or DL-DCI) to UE 110 and, inresponse, UE 110 may report the current ACK/NACK status of signaled HARprocess(es) as part of the DCI. The signaling of the HARQ process(es)may be either explicit (e.g., using HARQ process number(s)) or implicit(e.g., through service identification such as for eMBB HARQprocess(es)). The content of the ACK/NACK report may be two-stateACK/NACK, three-state ACK/NACK for cancelled ACK/NACK, or “already sent”to specify that the ACK/NACK information has already been sent. Underthe proposed scheme, four states may also be possible such as, forexample and without limitation, ACK-sent, NACK-sent, ACT-not-sent,NACK-not-sent. Equivalently, the latest ACK/NACK and new data indicator(NDI) bit received with the associated DCI may be indicated for eachHARQ process.

Illustrative Implementations

FIG. 8 illustrates an example system 800 having at least an exampleapparatus 810 and an example apparatus 820 in accordance with animplementation of the present disclosure. Each of apparatus 810 andapparatus 820 may perform various functions to implement schemes,techniques, processes and methods described herein pertaining toon-demand transmission of aborted HARQ codebook(s) in mobilecommunications, including the various schemes described above withrespect to various proposed designs, concepts, schemes, systems andmethods described above as well as processes described below. Forinstance, apparatus 810 may be an example implementation of UE 110, andapparatus 820 may be an example implementation of network node 125.

Each of apparatus 810 and apparatus 820 may be a part of an electronicapparatus, which may be a network apparatus or a UE (e.g., UE 110), suchas a portable or mobile apparatus, a wearable apparatus, a wirelesscommunication apparatus or a computing apparatus. For instance, each ofapparatus 810 and apparatus 820 may be implemented in a smartphone, asmart watch, a personal digital assistant, a digital camera, or acomputing equipment such as a tablet computer, a laptop computer or anotebook computer. Each of apparatus 810 and apparatus 820 may also be apart of a machine type apparatus, which may be an IoT apparatus such asan immobile or a stationary apparatus, a home apparatus, a wirecommunication apparatus or a computing apparatus. For instance, each ofapparatus 810 and apparatus 820 may be implemented in a smartthermostat, a smart fridge, a smart door lock, a wireless speaker or ahome control center. When implemented in or as a network apparatus,apparatus 810 and/or apparatus 820 may be implemented in a network node(e.g., network node 125), such as an eNB in an LTE, LTE-Advanced orLTE-Advanced Pro network or in a gNB or TRP in a 5G network, an NRnetwork or an IoT network.

In some implementations, each of apparatus 810 and apparatus 820 may beimplemented in the form of one or more integrated-circuit (IC) chipssuch as, for example and without limitation, one or more single-coreprocessors, one or more multi-core processors, one or morereduced-instruction set computing (RISC) processors, or one or morecomplex-instruction-set-computing (CISC) processors. In the variousschemes described above, each of apparatus 810 and apparatus 820 may beimplemented in or as a network apparatus or a UE. Each of apparatus 810and apparatus 820 may include at least some of those components shown inFIG. 8 such as a processor 812 and a processor 822, respectively, forexample. Each of apparatus 810 and apparatus 820 may further include oneor more other components not pertinent to the proposed scheme of thepresent disclosure (e.g., internal power supply, display device and/oruser interface device), and, thus, such component(s) of apparatus 810and apparatus 820 are neither shown in FIG. 8 nor described below in theinterest of simplicity and brevity.

In one aspect, each of processor 812 and processor 822 may beimplemented in the form of one or more single-core processors, one ormore multi-core processors, one or more RISC processors or one or moreCISC processors. That is, even though a singular term “a processor” isused herein to refer to processor 812 and processor 822, each ofprocessor 812 and processor 822 may include multiple processors in someimplementations and a single processor in other implementations inaccordance with the present disclosure. In another aspect, each ofprocessor 812 and processor 822 may be implemented in the form ofhardware (and, optionally, firmware) with electronic componentsincluding, for example and without limitation, one or more transistors,one or more diodes, one or more capacitors, one or more resistors, oneor more inductors, one or more memristors and/or one or more varactorsthat are configured and arranged to achieve specific purposes inaccordance with the present disclosure. In other words, in at least someimplementations, each of processor 812 and processor 822 is aspecial-purpose machine specifically designed, arranged and configuredto perform specific tasks including those pertaining to on-demandtransmission of aborted HARQ codebook(s) in mobile communications inaccordance with various implementations of the present disclosure.

In some implementations, apparatus 810 may also include a transceiver816 coupled to processor 812. Transceiver 816 may be capable ofwirelessly transmitting and receiving data. In some implementations,apparatus 820 may also include a transceiver 826 coupled to processor822. Transceiver 826 may include a transceiver capable of wirelesslytransmitting and receiving data.

In some implementations, apparatus 810 may further include a memory 814coupled to processor 812 and capable of being accessed by processor 812and storing data therein. In some implementations, apparatus 820 mayfurther include a memory 824 coupled to processor 822 and capable ofbeing accessed by processor 822 and storing data therein. Each of memory814 and memory 824 may include a type of random-access memory (RAM) suchas dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM) and/orzero-capacitor RAM (Z-RAM). Alternatively, or additionally, each ofmemory 814 and memory 824 may include a type of read-only memory (ROM)such as mask ROM, programmable ROM (PROM), erasable programmable ROM(EPROM) and/or electrically erasable programmable ROM (EEPROM).Alternatively, or additionally, each of memory 814 and memory 824 mayinclude a type of non-volatile random-access memory (NVRAM) such asflash memory, solid-state memory, ferroelectric RAM (FeRAM),magnetoresistive RAM (MRAM) and/or phase-change memory.

Each of apparatus 810 and apparatus 820 may be a communication entitycapable of communicating with each other using various proposed schemesin accordance with the present disclosure. For illustrative purposes andwithout limitation, a description of capabilities of apparatus 810, as aUE, and apparatus 820, as a base station of a serving cell of a wirelessnetwork (e.g., 5G/NR mobile network), is provided below. It isnoteworthy that, although the example implementations described beloware provided in the context of a UE, the same may be implemented in andperformed by a base station. Thus, although the following description ofexample implementations pertains to apparatus 810 as a UE (e.g., UE110), the same is also applicable to apparatus 820 as a network node orbase station such as a gNB, TRP or eNodeB (e.g., network node 125) of awireless network (e.g., wireless network 120) such as a 8G NR mobilenetwork.

Under a proposed scheme in accordance with the present disclosure,processor 812 of apparatus 810 may abort a transmission of a firstmessage of a first type of traffic to a wireless network (e.g., wirelessnetwork 120) via apparatus 820 in a first slot or sub-slot withoutresuming the transmission in the first slot or sub-slot. Additionally,processor 812 may store, in memory 814, a payload of the first message.Moreover, processor 812 may retransmit, via transceiver 816, the payloadin full to the wireless network via apparatus 820 in a second slot orsub-slot that is subsequent the first slot or sub-slot.

In some implementations, in aborting the transmission of the firstmessage, processor 812 may abort the transmission of the first messageupon detecting that a transmission of a second message of a second typeof traffic is also scheduled for the first slot or sub-slot, and whereina priority of the second type of traffic is higher than a priority ofthe first type of traffic.

In some implementations, the first message may include a first HARQcodebook for the first type of traffic, and the second message mayinclude a second HARQ codebook for the second type of traffic. In suchcases, the first type of traffic may include an eMBB traffic, and thesecond type of traffic may include a URLLC traffic.

In some implementations, in storing the payload of the first message,processor 812 may store at most one payload at a time such that: (a) anystored payload of any earlier message is overwritten by the payload ofthe first message, and (b) the payload of the first message is storeduntil overwritten by a second payload of a later message for which atransmission thereof is aborted subsequent to the second slot orsub-slot.

In some implementations, in storing the payload of the first message,processor 812 may store more than one payload at a time such that aplurality of payloads including the payload of the first message arestored according to a FIFO arrangement until an earliest payload of theplurality of payloads is overwritten by a new payload of a new messagefor which a transmission thereof is aborted subsequent to the secondslot or sub-slot.

In some implementations, in storing the payload of the first message,processor 812 may store a respective payload associated with eachtransmission whether aborted or not such that one payload associatedwith a later transmission is stored to overwrite another payloadassociated with an earlier transmission.

In some implementations, in retransmitting the payload in the secondslot or sub-slot, processor 812 may autonomously transmit the payloadusing an originally assigned PUCCH resource in the second slot orsub-slot.

In some implementations, in retransmitting the payload, processor 812may perform certain operations. For instance, processor 812 may receive,via transceiver 816, a trigger from the wireless network via apparatus820. Moreover, processor 812 may retransmit, via transceiver 816, thepayload in a PUSCH responsive to receiving the trigger.

In some implementations, in receiving the trigger, processor 812 mayreceive an UL-DCI signaling with the trigger indicated by a new DCIfield or an existing DCI field. In an event that the trigger isindicated by the new DCI field, the new DCI field may include either asingle bit or one or more slot indices pointing back in time andselecting the payload for retransmission. In an event that the triggeris indicated by the existing DCI field, a RRC-configurable value of anA-CSI field may trigger the retransmitting.

In some implementations, in retransmitting the payload, processor 812may perform certain operations. For instance, processor 812 may receive,via transceiver 816, a trigger from the wireless network via apparatus820. In response to receiving the trigger, processor 812 may performsome operations. For instance, processor 812 may concatenate the payloadwith one or more other payloads to form concatenated payloads. Moreover,processor 812 may transmit, via transceiver 816, the concatenatedpayloads in a PUCCH.

In some implementations, in receiving the trigger, processor 812 mayreceive a DL-DCI signaling from the wireless network via apparatus 820with the trigger indicated by a new DCI field or an existing DCI field.In an event that the trigger is indicated by the new DCI field, the newDCI field may include either a single bit or one or more slot indicespointing back in time and selecting the one or more other payloads. Inan event that the trigger is indicated by the existing DCI field, theexisting DCI field may include either: (a) a pre-configured value of aparameter (K1) that specifies HARQ ACK/NACK timing for a specific PDSCH;or (b) a pre-configured value of a HARQ process ID or a value in anotherfield different from the K1.

Alternatively, the trigger may be implicitly indicated based on a RNTIor a search space.

In some implementations, in transmitting the concatenated payloads inthe PUCCH, processor 812 may transmit the concatenated payloads in anearliest PUCCH after a current slot or sub-slot.

In some implementations, in retransmitting the payload, processor 812may transmit a single HARQ codebook, multiple HARQ codebooks that areselected, or all stored HARQ codebooks associated with transmissionspreviously aborted. In an event that the retransmitting of the payloadinvolves transmitting the multiple HARQ codebooks, the multiple HARQcodebooks may be selected by a DCI signaling from the wireless networkthat specifies an ordered list of pointers selecting previous slots orsub-slots during which transmissions of the multiple HARQ codebooks wereaborted. In an event that the retransmitting of the payload involvestransmitting all the stored HARQ codebooks associated with thetransmissions previously aborted, the retransmitting of the payload mayfurther involve transmitting a report containing a plurality of pointerseach pointing to a respective previous slot or sub-slot for each of allthe stored HARQ codebooks. In such cases, the ordered list may include abitmap (e.g., 16-bit bitmap) having a plurality of bits each of whichrepresenting a respective one of the previous slots or sub-slots.

Under a proposed scheme in accordance with the present disclosure,processor 812 of apparatus 810 may receive, via transceiver 816, atrigger from a wireless network (e.g., wireless network 120) viaapparatus 820. Moreover, processor 812 may report, via transceiver 816,status of one or more HARQ processes to the wireless network responsiveto receiving the trigger.

In some implementations, the trigger may include a DCI signaling (e.g.,UL-DCI or DL-DCI). In such cases, in reporting the status of the one ormore HARQ processes, processor 812 may report current ACK/NACK status ofall HARQ processes configured by the wireless network. Alternatively,processor 812 may report current ACK/NACK status of at least one HARQprocess signaled by the trigger either explicitly by an associated HARQprocess number or implicitly by an associated service identification.

Illustrative Processes

FIG. 9 illustrates an example process 900 in accordance with animplementation of the present disclosure. Process 900 may represent anaspect of implementing various proposed designs, concepts, schemes,systems and methods described above. More specifically, process 900 mayrepresent an aspect of the proposed concepts and schemes pertaining toon-demand transmission of aborted HARQ codebook(s) in mobilecommunications in accordance with the present disclosure. Process 900may include one or more operations, actions, or functions as illustratedby one or more of blocks 910, 920 and 930. Although illustrated asdiscrete blocks, various blocks of process 900 may be divided intoadditional blocks, combined into fewer blocks, or eliminated, dependingon the desired implementation. Moreover, the blocks/sub-blocks ofprocess 900 may be executed in the order shown in FIG. 9 or,alternatively in a different order. Furthermore, one or more of theblocks/sub-blocks of process 900 may be executed repeatedly oriteratively. Process 900 may be implemented by or in apparatus 810 andapparatus 820 as well as any variations thereof. Solely for illustrativepurposes and without limiting the scope, process 900 is described belowin the context of apparatus 810 as a UE (e.g., UE 110) and apparatus 820as a network node (e.g., network node 125) of a wireless network (e.g.,wireless network 120) such as a 5G/NR mobile network. Process 900 maybegin at block 910.

At 910, process 900 may involve processor 812 of apparatus 810 abortinga transmission of a first message of a first type of traffic to awireless network (e.g., wireless network 120) via apparatus 820 in afirst slot or sub-slot without resuming the transmission in the firstslot or sub-slot. Process 900 may proceed from 910 to 920.

At 920, process 900 may involve processor 812 storing, in memory 814, apayload of the first message. Process 900 may proceed from 920 to 930.

At 930, process 900 may involve processor 812 retransmitting, viatransceiver 816, the payload in full to the wireless network viaapparatus 820 in a second slot or sub-slot that is subsequent the firstslot or sub-slot.

In some implementations, in aborting the transmission of the firstmessage, process 900 may involve processor 812 aborting the transmissionof the first message upon detecting that a transmission of a secondmessage of a second type of traffic is also scheduled for the first slotor sub-slot, and wherein a priority of the second type of traffic ishigher than a priority of the first type of traffic.

In some implementations, the first message may include a first HARQcodebook for the first type of traffic, and the second message mayinclude a second HARQ codebook for the second type of traffic. In suchcases, the first type of traffic may include an eMBB traffic, and thesecond type of traffic may include a URLLC traffic.

In some implementations, in storing the payload of the first message,process 900 may involve processor 812 storing at most one payload at atime such that: (a) any stored payload of any earlier message isoverwritten by the payload of the first message, and (b) the payload ofthe first message is stored until overwritten by a second payload of alater message for which a transmission thereof is aborted subsequent tothe second slot or sub-slot.

In some implementations, in storing the payload of the first message,process 900 may involve processor 812 storing more than one payload at atime such that a plurality of payloads including the payload of thefirst message are stored according to a FIFO arrangement until anearliest payload of the plurality of payloads is overwritten by a newpayload of a new message for which a transmission thereof is abortedsubsequent to the second slot or sub-slot.

In some implementations, in storing the payload of the first message,process 900 may involve processor 812 storing a respective payloadassociated with each transmission whether aborted or not such that onepayload associated with a later transmission is stored to overwriteanother payload associated with an earlier transmission.

In some implementations, in retransmitting the payload in the secondslot or sub-slot, process 900 may involve processor 812 autonomouslytransmitting the payload using an originally assigned PUCCH resource inthe second slot or sub-slot.

In some implementations, in retransmitting the payload, process 900 mayinvolve processor 812 performing certain operations. For instance,process 900 may involve processor 812 receiving, via transceiver 816, atrigger from the wireless network via apparatus 820. Moreover, process900 may involve processor 812 retransmitting, via transceiver 816, thepayload in a PUSCH responsive to receiving the trigger.

In some implementations, in receiving the trigger, process 900 mayinvolve processor 812 receiving an UL-DCI signaling with the triggerindicated by a new DCI field or an existing DCI field. In an event thatthe trigger is indicated by the new DCI field, the new DCI field mayinclude either a single bit or one or more slot indices pointing back intime and selecting the payload for retransmission. In an event that thetrigger is indicated by the existing DCI field, a RRC-configurable valueof an A-CSI field may trigger the retransmitting.

In some implementations, in retransmitting the payload, process 900 mayinvolve processor 812 performing certain operations. For instance,process 900 may involve processor 812 receiving, via transceiver 816, atrigger from the wireless network via apparatus 820. In response toreceiving the trigger, process 900 may involve processor 812 performingsome operations. For instance, process 900 may involve processor 812concatenating the payload with one or more other payloads to formconcatenated payloads. Moreover, process 900 may involve processor 812transmitting, via transceiver 816, the concatenated payloads in a PUCCH.

In some implementations, in receiving the trigger, process 900 mayinvolve processor 812 receiving a DL-DCI signaling from the wirelessnetwork via apparatus 820 with the trigger indicated by a new DCI fieldor an existing DCI field. In an event that the trigger is indicated bythe new DCI field, the new DCI field may include either a single bit orone or more slot indices pointing back in time and selecting the one ormore other payloads. In an event that the trigger is indicated by theexisting DCI field, the existing DCI field may include either: (a) apre-configured value of a parameter (K1) that specifies HARQ ACK/NACKtiming for a specific PDSCH; or (b) a pre-configured value of a HARQprocess ID or a value in another field different from the K1.

Alternatively, the trigger may be implicitly indicated based on a RNTIor a search space.

In some implementations, in transmitting the concatenated payloads inthe PUCCH, process 900 may involve processor 812 transmitting theconcatenated payloads in an earliest PUCCH after a current slot orsub-slot.

In some implementations, in retransmitting the payload, process 900 mayinvolve processor 812 transmitting a single HARQ codebook, multiple HARQcodebooks that are selected, or all stored HARQ codebooks associatedwith transmissions previously aborted. In an event that theretransmitting of the payload involves transmitting the multiple HARQcodebooks, the multiple HARQ codebooks may be selected by a DCIsignaling from the wireless network that specifies an ordered list ofpointers selecting previous slots or sub-slots during whichtransmissions of the multiple HARQ codebooks were aborted. In an eventthat the retransmitting of the payload involves transmitting all thestored HARQ codebooks associated with the transmissions previouslyaborted, the retransmitting of the payload may further involvetransmitting a report containing a plurality of pointers each pointingto a respective previous slot or sub-slot for each of all the storedHARQ codebooks. In such cases, the ordered list may include a bitmap(e.g., 16-bit bitmap) having a plurality of bits each of whichrepresenting a respective one of the previous slots or sub-slots.

FIG. 10 illustrates an example process 1000 in accordance with animplementation of the present disclosure. Process 1000 may represent anaspect of implementing various proposed designs, concepts, schemes,systems and methods described above. More specifically, process 1000 mayrepresent an aspect of the proposed concepts and schemes pertaining toon-demand transmission of aborted HARQ codebook(s) in mobilecommunications in accordance with the present disclosure. Process 1000may include one or more operations, actions, or functions as illustratedby one or more of blocks 1010 and 1020. Although illustrated as discreteblocks, various blocks of process 1000 may be divided into additionalblocks, combined into fewer blocks, or eliminated, depending on thedesired implementation. Moreover, the blocks/sub-blocks of process 1000may be executed in the order shown in FIG. 10 or, alternatively in adifferent order. Furthermore, one or more of the blocks/sub-blocks ofprocess 1000 may be executed repeatedly or iteratively. Process 1000 maybe implemented by or in apparatus 810 and apparatus 820 as well as anyvariations thereof. Solely for illustrative purposes and withoutlimiting the scope, process 1000 is described below in the context ofapparatus 810 as a UE (e.g., UE 110) and apparatus 820 as a network node(e.g., network node 125) of a wireless network (e.g., wireless network120) such as a 5G/NR mobile network. Process 1000 may begin at block1010.

At 1010, process 1000 may involve processor 812 of apparatus 810receiving, via transceiver 816, a trigger from a wireless network (e.g.,wireless network 120) via apparatus 820. Process 1000 may proceed from1010 to 1020.

At 1020, process 1000 may involve processor 812 reporting, viatransceiver 816, status of one or more HARQ processes to the wirelessnetwork responsive to receiving the trigger.

In some implementations, the trigger may include a DCI signaling (e.g.,UL-DCI or DL-DCI). In such cases, in reporting the status of the one ormore HARQ processes, process 1000 may involve processor 812 reportingcurrent ACK/NACK status of all HARQ processes configured by the wirelessnetwork. Alternatively, process 1000 may involve processor 812 reportingcurrent ACK/NACK status of at least one HARQ process signaled by thetrigger either explicitly by an associated HARQ process number orimplicitly by an associated service identification.

ADDITIONAL NOTES

The herein-described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely examples, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

Further, with respect to the use of substantially any plural and/orsingular terms herein, those having skill in the art can translate fromthe plural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

Moreover, it will be understood by those skilled in the art that, ingeneral, terms used herein, and especially in the appended claims, e.g.,bodies of the appended claims, are generally intended as “open” terms,e.g., the term “including” should be interpreted as “including but notlimited to,” the term “having” should be interpreted as “having atleast,” the term “includes” should be interpreted as “includes but isnot limited to,” etc. It will be further understood by those within theart that if a specific number of an introduced claim recitation isintended, such an intent will be explicitly recited in the claim, and inthe absence of such recitation no such intent is present. For example,as an aid to understanding, the following appended claims may containusage of the introductory phrases “at least one” and “one or more” tointroduce claim recitations. However, the use of such phrases should notbe construed to imply that the introduction of a claim recitation by theindefinite articles “a” or “an” limits any particular claim containingsuch introduced claim recitation to implementations containing only onesuch recitation, even when the same claim includes the introductoryphrases “one or more” or “at least one” and indefinite articles such as“a” or “an,” e.g., “a” and/or “an” should be interpreted to mean “atleast one” or “one or more;” the same holds true for the use of definitearticles used to introduce claim recitations. In addition, even if aspecific number of an introduced claim recitation is explicitly recited,those skilled in the art will recognize that such recitation should beinterpreted to mean at least the recited number, e.g., the barerecitation of “two recitations,” without other modifiers, means at leasttwo recitations, or two or more recitations. Furthermore, in thoseinstances where a convention analogous to “at least one of A, B, and C,etc.” is used, in general such a construction is intended in the senseone having skill in the art would understand the convention, e.g., “asystem having at least one of A, B, and C” would include but not belimited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc. In those instances where a convention analogous to “atleast one of A, B, or C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention, e.g., “a system having at least one of A, B, or C” wouldinclude but not be limited to systems that have A alone, B alone, Calone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc. It will be further understood by those withinthe art that virtually any disjunctive word and/or phrase presenting twoor more alternative terms, whether in the description, claims, ordrawings, should be understood to contemplate the possibilities ofincluding one of the terms, either of the terms, or both terms. Forexample, the phrase “A or B” will be understood to include thepossibilities of “A” or “B” or “A and B.”

From the foregoing, it will be appreciated that various implementationsof the present disclosure have been described herein for purposes ofillustration, and that various modifications may be made withoutdeparting from the scope and spirit of the present disclosure.Accordingly, the various implementations disclosed herein are notintended to be limiting, with the true scope and spirit being indicatedby the following claims.

What is claimed is:
 1. A method, comprising: aborting, by a processor ofan apparatus, a transmission of a first message of a first type oftraffic in a first slot or sub-slot without resuming the transmission inthe first slot or sub-slot; storing, by the processor, a payload of thefirst message; and retransmitting, by the processor, the payload in fullin a second slot or sub-slot that is subsequent the first slot orsub-slot, wherein the retransmitting of the payload comprisesretransmitting the payload responsive to receiving a trigger from awireless network, wherein the receiving of the trigger comprisesreceiving a downlink (DL) downlink control information (DL-DCI)signaling with the trigger indicated by an existing downlink controlinformation (DCI) field, and wherein the existing DCI field comprises apre-configured value of a hybrid automatic repeat request (HARQ) processidentification (ID) or a value in another field different from apre-configured value of a parameter (K1) that specifies HARQacknowledgement and negative acknowledgement (ACK/NACK) timing for aphysical downlink shared channel (PDSCH).
 2. The method of claim 1,wherein the aborting of the transmission of the first message comprisesaborting the transmission of the first message upon detecting that atransmission of a second message of a second type of traffic is alsoscheduled for the first slot or sub-slot, and wherein a priority of thesecond type of traffic is higher than a priority of the first type oftraffic.
 3. The method of claim 2, wherein the first message comprises afirst HARQ codebook for the first type of traffic, wherein the secondmessage comprises a second HARQ codebook for the second type of traffic,wherein the first type of traffic comprises an enhanced Mobile Broadband(eMBB) traffic, and wherein the second type of traffic comprises aUltra-Reliable Low-Latency Communication (URLLC) traffic.
 4. The methodof claim 1, wherein the storing of the payload of the first messagecomprises storing at most one payload at a time such that: any storedpayload of any earlier message is overwritten by the payload of thefirst message, and the payload of the first message is stored untiloverwritten by a second payload of a later message for which atransmission thereof is aborted subsequent to the second slot orsub-slot.
 5. The method of claim 1, wherein the storing of the payloadof the first message comprises storing more than one payload at a timesuch that a plurality of payloads including the payload of the firstmessage are stored according to a first-in-first-out (FIFO) arrangementuntil an earliest payload of the plurality of payloads is overwritten bya new payload of a new message for which a transmission thereof isaborted subsequent to the second slot or sub-slot.
 6. The method ofclaim 1, wherein the storing of the payload of the first messagecomprises storing a respective payload associated with each transmissionwhether aborted or not such that one payload associated with a latertransmission is stored to overwrite another payload associated with anearlier transmission.
 7. The method of claim 1, wherein theretransmitting of the payload in the second slot or sub-slot comprisesautonomously transmitting the payload using an originally assignedphysical uplink control channel (PUCCH) resource in the second slot orsub-slot.
 8. The method of claim 1, wherein the retransmitting of thepayload comprises: receiving, by the processor, a trigger from awireless network; and retransmitting, by the processor, the payload in aphysical uplink shared channel (PUSCH) responsive to receiving thetrigger.
 9. The method of claim 8, wherein the receiving of the triggercomprises receiving an uplink downlink control information (UL-DCI)signaling with the trigger indicated by a new downlink controlinformation (DCI) field or an existing DCI field.
 10. The method ofclaim 9, wherein: a radio resource control (RRC)-configurable value ofan aperiodic channel state information (A-CSI) field triggers theretransmitting.
 11. The method of claim 1, wherein the retransmitting ofthe payload further comprises: responsive to receiving the trigger,performing, by the processor: concatenating the payload with one or moreother payloads to form concatenated payloads; and transmitting theconcatenated payloads in a physical uplink control channel (PUCCH). 12.The method of claim 11, wherein the trigger is implicitly indicatedbased on a radio network temporary identifier (RNTI) or a search space.13. The method of claim 11, wherein the transmitting of the concatenatedpayloads in the PUCCH comprises transmitting the concatenated payloadsin an earliest PUCCH after a current slot or sub-slot.
 14. The method ofclaim 1, wherein the retransmitting of the payload comprisestransmitting a single HARQ codebook, multiple HARQ codebooks that areselected, or all stored HARQ codebooks associated with transmissionspreviously aborted.
 15. The method of claim 14, wherein: in an eventthat the retransmitting of the payload comprises transmitting themultiple HARQ codebooks, the multiple HARQ codebooks are selected by aDCI signaling from a wireless network that specifies an ordered list ofpointers selecting previous slots or sub-slots during whichtransmissions of the multiple HARQ codebooks were aborted, and in anevent that the retransmitting of the payload comprises transmitting allthe stored HARQ codebooks associated with the transmissions previouslyaborted, the retransmitting of the payload further comprisestransmitting a report containing a plurality of pointers each pointingto a respective previous slot or sub-slot for each of all the storedHARQ codebooks.
 16. The method of claim 15, wherein the ordered listcomprises a bitmap having a plurality of bits each of which representinga respective one of the previous slots or sub-slots.
 17. A method,comprising: receiving, by a processor of an apparatus, a trigger from awireless network; and reporting, by the processor, status of one or morehybrid automatic repeat request (HARQ) processes to the wireless networkresponsive to receiving the trigger, wherein the trigger comprises adownlink (DL) downlink control information (DL-DCI) signaling with thetrigger indicated by an existing downlink control information (DCI)field, and wherein the existing DCI field comprises a pre-configuredvalue of a HARQ process identification (ID) or a value in another fielddifferent from a pre-configured value of a parameter (K1) that specifiesHARQ acknowledgement and negative acknowledgement (ACK/NACK) timing fora physical downlink shared channel (PDSCH).
 18. The method of claim 17,wherein the trigger comprises a DCI signaling, and wherein the reportingof the status of the one or more HARQ processes comprises: reportingcurrent ACK/NACK status of all HARQ processes configured by the wirelessnetwork; or reporting current ACK/NACK status of at least one HARQprocess signaled by the trigger either explicitly by an associated HARQprocess number or implicitly by an associated service identification.